Your comments are welcome on this matter, and your suggestions may be added to this file.
Many thanks to those who have contributed to MUBBS and supplied me with some of the following ideas and text.
I'd like to see a "Visual" BBS editor. That's were MUBBS would be laid out with small boxes and have lines connecting them to show program flow. Sort of like a flow chart bu more advanced. Clicking on each box would let you make changes and edit that section only.
This way the Sysop could layout his/her MUBBS any way they wanted and not be tied into one specific interface. Hermes is nice but I'd like to be able to customize it more.
SysOps should be able to run multiple BBSs simultaneously. Users of one BBS would not be able to tell that the other BBSs exist. Multiple BBSs may or may not share message and file sections, at the SysOps's discretion. (this can be done now, set up a menu module that the user chooses whice system to log into, then call login for each system).
the front end issue...
The system should be able to, within reason, update (or do other fancy things) to the user front-end software. To this end, an intelligent/programmable front end might best be built in HyperCard or SuperCard. Welcome messages, menus, images etc. which change infrequently could be stored by the system into the user's front end to speed navigation. On log-in MUBBS could ask the front end for the date of its last log-in, then update only those interface features which have since been changed.
